-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(ecs): ContainerImage.fromDockerImageAsset #6093
Conversation
Allow using an existing `DockerImageAsset` object as a container image in order to enable direct access to `DockerImageAsset`s API such as accessing the ECR repository, the source hash or granting permissions. The reason this could not have been exposed through the normal `fromImageAsset` is that `ContainerImage` can be used multiple times (i.e. be bound to multiple container definitions), so there is no reliable way to allow users to access the asset. Related to #5791 and #5983
🚫 Features must contain a change to a README file |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Had one minor comment. Added the do not merge tag, and approved it as everything else lgtm. Feel free to remove the tag
readonly directory: string; | ||
|
||
/** | ||
* Options for DockerImageAsset |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you think we can be more descriptive as to when users should use DockerImageAssetOptions vs DockerImageAssetProps? (we've had users who have been confused with ContainerDefinitionOptions vs ContainerDefinitionProps in the past)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure there is something super smart to write here... Maybe something like "includes all the optional configuration" (without the mandatory one)...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll update in a subsequent commit. Let me know what you think.
Thank you for contributing! Your pull request is now being automatically merged. |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
Allow using an existing
DockerImageAsset
object as a container image in order to enable direct access toDockerImageAsset
s API such as accessing the ECR repository, the source hash or granting permissions.The reason this could not have been exposed through the normal
fromImageAsset
is thatContainerImage
can be used multiple times (i.e. be bound to multiple container definitions), so there is no reliable way to allow users to access the asset.Related to #5791 and #5983
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license